Landmark Store topic

Landmark stores provide persistent storage, import, and browsing capabilities for points of interest. Use these features to create and manage named stores, import or edit landmark collections, and control which stores and categories are visible in map views.

• LandmarkStoreService: Use this service-level API to create, register, discover, and remove landmark stores. It exposes access to special-purpose stores and global listings used by application or map-level preferences.
• LandmarkStore: Use this model to represent a single persistent collection of landmarks and categories. It is responsible for storing, importing, updating, and removing individual landmarks and maintaining category metadata.
• LandmarkStoreCollection: Use this collection to manage multiple landmark stores and their enabled categories. It is commonly used by map view preferences to control which stores and categories are visible.
• LandmarkStoreListener: Use this listener to react to landmark and store lifecycle events, including creation, updates, removals, and browse session invalidation. It enables real-time UI updates when store content changes.
• LandmarkBrowseSession: Use this session object to iterate, filter, and sort landmarks from a store according to browsing settings. It provides paged or filtered access suitable for UI browsing and search flows.

These components work together to offer consistent, persistent landmark management: LandmarkStoreService manages store lifecycle, LandmarkStore contains the landmark data, LandmarkStoreCollection aggregates stores for views, LandmarkStoreListener provides event notifications, and LandmarkBrowseSession supports browsing and filtering. Together they enable dependable POI workflows, geofencing, and user-driven landmark editing.

For typical usage, create or open LandmarkStore instances via LandmarkStoreService, and expose store collections to your map UI through LandmarkStoreCollection. Subscribe with LandmarkStoreListener to keep UIs in sync and use LandmarkBrowseSession for efficient paging and filtering in listing interfaces.

Learn more about landmark stores: https://developer.magiclane.com/docs/flutter/guides/core/landmarks#landmark-stores